home *** CD-ROM | disk | FTP | other *** search
- Path: howland.reston.ans.net!psinntp!psinntp!psinntp!psinntp!usenet
- From: grantp@usa.pipeline.com(Pete Grant)
- Newsgroups: comp.lang.c++
- Subject: Re: VC++ 4.0 memory
- Date: 14 Apr 1996 22:40:22 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4krusm$m1@news1.h1.usa.pipeline.com>
- References: <4krk06$r8l@news.acns.nwu.edu>
- NNTP-Posting-Host: 38.8.120.17
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete Grant)
- X-Newsreader: Pipeline v3.5.0
-
- On Apr 14, 1996 19:34:30 in article <VC++ 4.0 memory>,
- 'jhgreen@labrador.res-hall.nwu.edu (Jed Greene)' wrote:
-
-
- >I am planning on purchasing VC++ 4.0 but I have a few questions.
- >First, will I have flat memory addressing (huge arrays painlessly)?
-
- Yes. No more segments nor near/far stuff.
-
- >Also, if I compile on 95, will I be able to create applications that
- >run on NT?
-
- Yes. There are some differences in the WIN32 API between
- NT and Win95, but chances are you won't run into them --
- at first, anyway. Typically, the same binaries will
- run on both platforms.
-
- What about 16 bit stuff for 3.1?
-
- Yes and No. MSVC++4.x is a 32-bit only system. If you
- limit your code to Win32S and install Win32S on the target
- Win31 machine, it is possible to run MSVC++ generated
- programs. Win32S does not have threads so you must use
- the single-threaded library.
-
- I'm not sure if you can use MFC in a Win32S program
- since MFC is multi-threaded. Maybe someone else can
- shed some light on this topic.
-
- BTW, MSVC++4.0 includes MSVC++1.52 for developing 16-bit
- programs. IMHO this is of limited use since the code
- is most likely not compatible between the two systems.
-
- --
- Pete Grant
- Kalevi, Inc.
- Software Engineering & development
-